|
Apache Tapestry is an open-source component-oriented Java web application framework conceptually similar to JavaServer Faces and Apache Wicket.〔(【引用サイトリンク】title=Howard Lewis Ship of Tapestry interview (1 ) (2012-10-22) )〕 Tapestry was created by Howard Lewis Ship, and was adopted by the Apache Software Foundation as a top-level project in 2006.〔Drobiazko 2012, p. 1.〕 Tapestry emphasizes simplicity, ease of use, and developer productivity. It adheres to the Convention over Configuration paradigm, eliminating almost all XML configuration.〔http://tapestryjava.blogspot.com/2006/07/tapestry-5-updates.html〕 Tapestry uses a modular approach to web development, by having a strong binding between each user interface component (object) on the web page and its corresponding Java class. This component-based architecture borrows many ideas from WebObjects.〔Tapestry in Action - Preface by Howard Lewis Ship〕 == Notable Features == ; Live Class Reloading : Tapestry monitors the file system for changes to Java page classes, component classes, service implementation classes, HTML templates and component property files, and it hot-swaps the changes into the running application without requiring a restart. This provides a very short code-save-view feedback cycle that is claimed to greatly improve developer productivity.〔http://tapestry.apache.org/class-reloading.html〕 ; Component-based : Pages may be constructed with small nestable components, each having a template and component class. Custom components are purportedly trivial to construct.〔Drobiazko 2012, p. 20.〕 ; Convention over configuration : Tapestry uses naming conventions and annotations, rather than XML, to configure the application.〔Drobiazko 2012, p. 7.〕 ; Spare use of HTTPSession : By making minimal use of the HTTPSession, Tapestry is designed to be highly efficient in a clustered, session-replicated environment.〔http://tapestry.apache.org/performance-and-clustering.html〕 ; Post/Redirect/Get : Most form submissions follow the Post/Redirect/Get (PRG) pattern, which reduces multiple form submission accidents and makes URLs friendlier and more bookmarkable, along with enabling the browser Back and Refresh buttons to operate normally.〔http://tapestry.apache.org/forms-and-validation.html〕 ; Inversion of Control (IOC) : Tapestry is built on a lightweight Inversion of Control layer with similarities to Google Guice but designed to make nearly all aspects of Tapestry's behavior configurable and replaceable.〔Drobiazko 2012, p. 7.〕 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Apache Tapestry is an open-source component-oriented Java web application framework conceptually similar to JavaServer Faces and Apache Wicket.(【引用サイトリンク】title=Howard Lewis Ship of Tapestry interview (1 ) (2012-10-22) ) Tapestry was created by Howard Lewis Ship, and was adopted by the Apache Software Foundation as a top-level project in 2006.Drobiazko 2012, p. 1.Tapestry emphasizes simplicity, ease of use, and developer productivity. It adheres to the Convention over Configuration paradigm, eliminating almost all XML configuration.http://tapestryjava.blogspot.com/2006/07/tapestry-5-updates.html Tapestry uses a modular approach to web development, by having a strong binding between each user interface component (object) on the web page and its corresponding Java class. This component-based architecture borrows many ideas from WebObjects.Tapestry in Action - Preface by Howard Lewis Ship== Notable Features ==; Live Class Reloading : Tapestry monitors the file system for changes to Java page classes, component classes, service implementation classes, HTML templates and component property files, and it hot-swaps the changes into the running application without requiring a restart. This provides a very short code-save-view feedback cycle that is claimed to greatly improve developer productivity.http://tapestry.apache.org/class-reloading.html; Component-based : Pages may be constructed with small nestable components, each having a template and component class. Custom components are purportedly trivial to construct.Drobiazko 2012, p. 20.; Convention over configuration : Tapestry uses naming conventions and annotations, rather than XML, to configure the application.Drobiazko 2012, p. 7.; Spare use of HTTPSession : By making minimal use of the HTTPSession, Tapestry is designed to be highly efficient in a clustered, session-replicated environment.http://tapestry.apache.org/performance-and-clustering.html; Post/Redirect/Get : Most form submissions follow the Post/Redirect/Get (PRG) pattern, which reduces multiple form submission accidents and makes URLs friendlier and more bookmarkable, along with enabling the browser Back and Refresh buttons to operate normally.http://tapestry.apache.org/forms-and-validation.html; Inversion of Control (IOC) : Tapestry is built on a lightweight Inversion of Control layer with similarities to Google Guice but designed to make nearly all aspects of Tapestry's behavior configurable and replaceable.Drobiazko 2012, p. 7.」の詳細全文を読む スポンサード リンク
|